-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix broken cross links in docs #392
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made some suggestions to fix some issues with the links.
Thanks for catching these!
Also, could you fix the 0.4.19 release notes? I can't easily suggest, but here:
docs/docs/release/release_0_4_19.md
Line 72 in d3d36cd
See the ["Deprecations" section below](#Deprecations) for more information on |
I think it needs to be (#deprecations)
(lower case d
)
(nap_9_design_and_architecture) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤦 I must have done this half asleep, will fix!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no worries 😄
and no rush!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually we can just use the old label, what doesn't work is the capitalization. So we can just change the reference to read (#ui-design-and-architecture)
(nap_9_implementation) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(nap_9_implementation) | |
(nap_9_implementation)= |
Same as above, the link doesn't work.
(dask_image)= | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(dask_image)= | |
(dask_image)= |
Right now the link below doesn't work. I think this is the fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah great! I was working on this too, so will submit a parallel PR but please let's merge this one first 😄
(nap_9_design_and_architecture) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually we can just use the old label, what doesn't work is the capitalization. So we can just change the reference to read (#ui-design-and-architecture)
### UI Design and Architecture | ||
Specific UI design and architecture remains to be determined. This will be explored as part of step 4 in the [Implementation Plan](#Implementation). UI design needs additional refinement and exploration, and this is expected to continue after basic/core implementation propsed in this NAP is complete. UI changes may also be described in a separate NAP along with a discussion of convenience functions and affordances for common operations. Some placeholder or experimental code will be used in the meantime as a prototype implementation. | ||
Specific UI design and architecture remains to be determined. This will be explored as part of step 4 in the [Implementation Plan](nap_9_implementation). UI design needs additional refinement and exploration, and this is expected to continue after basic/core implementation propsed in this NAP is complete. UI changes may also be described in a separate NAP along with a discussion of convenience functions and affordances for common operations. Some placeholder or experimental code will be used in the meantime as a prototype implementation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here, using just (#implementation)
works
@@ -205,7 +207,7 @@ directory. The dataset is 3.69 GB unzipped. | |||
``` | |||
|
|||
While we could use plain `dask` through `delayed`, as we have shown above, we | |||
will [make our lives easier](make-your-life-easier-with-dask-image) here and use | |||
will [make our lives easier](dask_images) here and use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfectly fine to create a new target, but FYI if we do [make our lives easier](#make-your-life-easier-with-dask-image)
the automatic label works.
Thanks for the explanations @melissawm |
@melissawm I will close this as you already address these in your #393 PR |
Our doc build has the following broken link warnings:
I've just used reference labels when the original title (?) labels have broken, reference labels seem easier and less brittle.
Note the last one, AFAICT there originally was a PR to add a
brain_dataset_tutorial/md
file: napari/napari.github.io#64But what got merged was: #132 where that example was just added to the
dask.md
file, so I've removed that reference from the list.